Universal Access To All Knowledge
Home Donate | Store | Blog | FAQ | Jobs | Volunteer Positions | Contact | Bios | Forums | Projects | Terms, Privacy, & Copyright
Search: Advanced Search
Anonymous User (login or join us)
Upload

Reply to this post | Go Back
View Post [edit]

Poster: Administrator, Curator, or StaffTyler Date: May 15, 2007 7:00pm
Forum: etree Subject: **From the LMA team: Important new info / updates on how your Archive.org uploads are handled. PLEASE READ**

*****
Hello Live Music Archive Patrons,


First off, thank you very much for sharing, taping, and uploading concerts over the past 5 years. Since the Fall of 2002 when the LMA got off the ground, we now have ~39,500 individual concerts by ~2,400 different bands, all for FREE and all above-board thanks to the hard work of dedicated fans of live music like you. By turning your friends onto the archive, as well as turning your favorite band on to the archive, we have made it the de-facto place to go to for taper friendly concerts to be downloaded, streamed, and preserved for not only months, but for decades into the future.

The project is still humming along nicely, but we recently tweaked the way shows are quality checked, to make sure that what we preserve is the highest quality for mass music / file distribution. That being said, we wanted to explain / put in print a few of the new features we've recently implemented to ensure quality control of the show files.

1. When you upload a show (using the steps outlined in the 'how-to' PDF here: http://www.archive.org/iathreads/uploaded-files/Brad_Leblanc-Uploading_to_LMA.pdf ) it goes through several checks:
* If an md5 is included, the files are checked against the md5. Please try and include an md5 with every upload.
* If the show you upload is a set of FLAC (*.flac) files, the system gets a list of all *.flac files in the item and runs "flac -t" on them (that tries to make sure they can be decoded). This "flac -t" process check's the .flac file's internal checksum.
* It checks to see if you have included a setlist / info text (.txt) file. This .txt file is a file, usually put together by the taper, that explains the recording notes, taper info, source info, venue, etc. The datacheck relating to the info.txt file is where the system makes sure you have a *.txt file (where filenames containing "md5|ffp|fingerprint" (case insensitive) don't count). This setlist file is mandatory and is necessary for the show fileset to be complete.

If any of these tasks fail, the 'derive' task in the item's history will change to a 'red-line' and you will be auto e-mailed about the problem. In the past, you as the uploader would only receive an auto e-mail if your md5 failed. We have fixed the bug and now all red row failures relating to "data integrity" (like MD5 checks, flac -t checking, or lack of a .txt file) will result in a more descriptive email to you, the uploader.

2. In regards to 'auto e-mails' that the system sends, in the past, these auto e-mails for failures had wording that was not fully clear. We have edited the verbiage to make the basic idea of "What do I have to do to fix this problem" come across better. These auto e-mails will now also contain the www.archive.org/details/ page link of your show (as well as the www.archive.org/checkout/ link). This means you can click on the details page of your show directly from the failure e-mail and look at your show to see what the e-mail is talking about. The 'checkout' link is the link you will need to click on to 'checkout' the show and make it 'editable' for whatever changes you need to do to it.

3. Upon any deriver red row failure for flac or md5 check failures, or missing .txt, the system will make all non-XML files non-downloadable. This is intended to 'stop the spread' of bad / corrupt files. What this means is that people won't be able to continue downloading music files if the show failed any of the checks. The details page itself will look 'normal' but if a user tries to click / download any of the music files, they will get a error page. By preventing these bad files from circulating, we will help keep the trading pool clean until the uploader can contact the LMA and work out / fix what they did wrong with their file set. Once things are straightened out, the show goes back to being fully downloadable. There is no 'time limit' on fixing your show either, so don't worry if it takes you a few days to get back to the LMA admins as far as fixing your bad track / show. Whenever it gets fixed, the system will make it downloadable again.

Thanks again for contributing so much to the Live Music Archive. Without the support of the bands and the tapers and fans and users like you, the project would have never been such a huge success. If you have more questions / want more clarity of how things work, please feel free to post a question and we'll answer it to the best of our ability.

The Live Music Archive team
**************

Reply to this post
Reply [edit]

Poster: snarkus Date: May 16, 2007 11:33am
Forum: etree Subject: Re: **From the LMA team: Important new info / updates on how your Archive.org uploads are handled. PLEASE READ**

thank you for putting this in place, especially adding the "what do i do now?" verbiage. i'm almost tempted to upload some corrupted files to see how it works out.

but i won't.

many thanks for all of your efforts.
the archive is nothing less than a national treasure.

Reply to this post
Reply [edit]

Poster: bradm Date: May 21, 2007 5:10am
Forum: etree Subject: Re: **From the LMA team: Important new info / updates on how your Archive.org uploads are handled. PLEASE READ**

I had an MD5 error in an upload I did yesterday

http://www.archive.org/details/acres2007-05-19.oktava.shnf

and followed the e-mailed instructions to check it out, after which re-uploaded the file that caused the problem, and responded to the e-mail. I got an "Auto-Reply" response, but the body of it was empty (so I assume it was just an acknowledgment), and there aren't any instructions as to what, if anyting, I can/should do next. The status of the upload in the contribution center listing is still red ("Waiting for admin"), which makes me think there isn't anything for me to do. Do I just have to wait?

Thanks,
Brad

Reply to this post
Reply [edit]

Poster: Administrator, Curator, or Staffchops11 Date: May 21, 2007 6:07am
Forum: etree Subject: Re: **From the LMA team: Important new info / updates on how your Archive.org uploads are handled. PLEASE READ**

Yes, you did everything right. An curator will come along and rerun it.

Reply to this post
Reply [edit]

Poster: bradm Date: May 21, 2007 6:10am
Forum: etree Subject: Re: **From the LMA team: Important new info / updates on how your Archive.org uploads are handled. PLEASE READ**

It looks like it's deriving now, so whoever kicked it into gear, thanks! (As an aside, it'd be nice if the auto-reply e-mail included some text, maybe "Thank you for responding. You contribution is in the queue for the admin to process" or something.)

Aloha,
Brad

Reply to this post
Reply [edit]

Poster: Administrator, Curator, or Staffchops11 Date: May 21, 2007 6:13am
Forum: etree Subject: Re: **From the LMA team: Important new info / updates on how your Archive.org uploads are handled. PLEASE READ**

What it actually does is opens up a error report in our tracking system. Then when a curator logs in and sees it, they will write you back telling you that they are running it again.

I thought that the error report system wrote back explaining that a ticket had been opened though, don't know why you got a blank email. I will look into it.

Terms of Use (10 Mar 2001)